handle new optional merge retry semantics - #34
Merged
Conversation
fat
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
merge()has two target-tip modes:expectedTargetShawhen the target branch must still point at a specific commit. If the target moved, the merge fails with 409.expectedTargetShawhen you want Code Storage to merge into the current target tip. For native Code Storage targets, the gateway may retry stale target or repository movement internally while keeping the originally resolved source commit pinned.This doesn't require any active changes to the SDK surface, this change just clarifies the two modes and makes the tests clearer.